ALL EDITORS V447 - SAVE GAME FOR EVERY PLAYER, RESUME SHOWS THE SAVES, NO PAUSE
(V446 base. V445/V446 account save folders save_/mpsave_/mpbsave_<account> unchanged.)

INSTALL (HOST PC)
  Close every BG2 window, extract the whole ZIP, run SETUP_IN_GAME_ACCOUNTS.bat
  (or UI Interface Editor > IN-GAME ACCOUNTS / SETUP > INSTALL / REPAIR V447).
  Same game folder and profile. Setup freezes the files again when it is done.
  Setup still requires the exact BaldurII.exe that V445 verified (see below).

1. SAVE GAME IN EVERY PLAYER'S IN-GAME MENU (Esc > SAVE GAME)
  - Host and single player: BG2's normal Save screen (as V446). The save goes
    to that account's own folder: save_<account> (single player),
    mpsave_<account> (SoA/ToB multiplayer), mpbsave_<account> (TBP multiplayer).
  - Joined player: BG2 itself refuses saves on a joined player's game (only
    the host's game holds the whole world), so V446's native screen could not
    work there. V447: the button asks the HOST's game to save the whole party
    as the PLAYER's save:  DRKnn_<player>_<campaign>_PARTY_Group Save
    The router then moves that save from mpsave_<host> (mpbsave_ for TBP) into
    mpsave_<player> (mpbsave_<player>), after BG2 has finished writing it.
    One Group Save per player and campaign; the next one replaces it.
    The player continues it from their own account (Resume Campaign / Load).
  - The host's game waits for a calm moment (world screen, no cutscene,
    dialogue, death or loading - up to 60 s) and writes the result in the
    multiplayer chat. The button tooltip says when the request was sent.
  - Only the player's own game window can ask, and only while logged in.

2. RESUME CAMPAIGN SHOWS THE SAVES FIRST
  Resume Campaign opens BG2's Load list of this account's saves. The newest
  save of the chosen campaign is SELECTED, nothing is loaded automatically.
  Click LOAD, or pick another save first. Loading also selects that save's
  campaign (for autosaves and joining).

3. NO PAUSE
  V444's Space-key guard only works if BG2 lets the interface see the Space
  key first. V447 no longer needs that: the host's (or single player's) window
  undoes ANY pause the game did not impose itself - Space, the clock, any
  re-bound pause key and auto-pause. Never undone: cutscenes, dialogue, death,
  engine hard pauses. Guests still have no Pause permission (V444).
  - Turn auto-pause options off in Options > Gameplay to avoid
    "paused / unpaused" messages; they are undone anyway.
  - It never fights a pause it cannot lift: 3 tries in 5 s, then 10 s rest.
  - One account can keep pausing (e.g. for testing): with that BG2 window
    closed, add to <profile>\<account>.lua:
        SetPrivateProfileString('Drakhysys','Allow Pause','1')
  - Last resort, no code needed: Options > Gameplay > Keyboard, give "Pause"
    an unused key. Each account keeps its own key binding (own <account>.lua).

4. UI INTERFACE EDITOR (START_UI_INTERFACE_EDITOR.bat > IN-GAME ACCOUNTS / SETUP)
  - INSTALL / REPAIR V447 runs the SAME installer as SETUP_IN_GAME_ACCOUNTS.bat
    and freezes the files when it is done.
  - CHECK ACCOUNT SETUP STATUS now also reports: Save Game in every player's
    menu, Resume shows the saves first, No pause.
  - NEW: ALLOW / BLOCK PAUSE FOR ONE ACCOUNT writes the Allow Pause line into
    that account's own .lua for you (BG2 closed; applies at its next start).
  - Window title and all labels say V447.

5. ACCOUNT SAVE FOLDERS (V445 executable patch) - WHAT WAS CHECKED
  - test_v447_save_resume.ExeSavePathPatchTests builds an image with the
    verified layout and checks that every patched instruction points at the
    account's own path (save_ / mpsave_ / mpbsave_, 11-letter names too), that
    no other byte changes, and that a different executable is refused.
  - NOT checkable without your BaldurII.exe: that the 12 listed instructions (10 path strings)
    are ALL the places BG2 uses those folders. Upload BaldurII.exe to have
    that verified.
  - Setup aborts on any other BaldurII.exe build (another store or a game
    update): nothing is changed then.

CHECKS (offline)
  python -m unittest test_v447_save_resume test_v444_ui_editor_account_setup -v
NOT TESTED HERE: real BG2 windows on Windows (saving, loading, moving the
Group Save, chat messages, pause behaviour in the real engine).
